• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    The invention relates to a flight data interface device (1) with a terminal interface for coupling the flight data interface device (1) to a terminal (3), in particular a check-in counter and / or a workstation of an employee at the gate, and a A dispatching system (DCS) interface (10), wherein the DCS interface (10) is adapted to couple the flight data interface device (1) to at least one remote DCS (2). The flight data interface device (1) further comprises a backup system (12). The backup system (12) is operably coupled to the terminal interface (11) and the DCS interface (10), wherein the backup system (12) is adapted to operate in a standby mode when operatively coupled to the DCS (2), and is further configured to operate temporarily in an active mode in a case where the operational coupling with the DCS (2) is temporarily interrupted and in the active mode as DCS for the terminal (3) to work. Furthermore, the invention relates to a method for operating a terminal (3) and a corresponding computer program product.
    公开号:CH710509B1
    申请号:CH01572/15
    申请日:2015-10-28
    公开日:2017-06-15
    发明作者:Kabilov Zafar；Niederhauser Markus
    申请人:Zamar Ag；
    IPC主号:
    专利说明:

    Description Technical Field The present invention is in the general technical field of the aerospace industry. In particular, it is in the area of communication between dispatching systems (DCSs) and airport terminals.
    STATE OF THE ART
    Passenger and baggage data, particularly passenger lists and additional cancellation lists, are generally stored and processed by dispatch systems (DCSs).
    The DCSs are part of the IT infrastructure of the airlines and are located worldwide in the planning and data centers of the airlines. For check-in and boarding, data exchange between terminals, in particular the employee's check-in desks and workstations at the departure gate at a departure airport, and the DCS of the corresponding airline is required. DCSs and data terminals are offered by a number of service providers. The data exchange between the DCSs and the terminals at the airport is typically based on Internet connections.
    SUMMARY OF THE DISCLOSURE [0004] If the data exchange between the terminals of the airport and a DCS is temporarily disrupted, disturbed, unstable, or the like (hereinafter collectively collectively referred to as "interrupted"), check-in and / or boarding can not be undertaken which can lead to potentially significant flight delays, financial losses and general disruption of air traffic. While temporary disruption of Internet connections is a general problem, it is particularly critical in countries and areas with comparatively low communication infrastructure, unstable power supply, and in situations of severe meteorological disturbances, natural disasters, or the like.
    Another problem with the connection between the DCSs and the terminals results from the fact that it is often desirable to connect one and the same terminal to different DCSs, which may be of different types and / or different ones Providers are provided. This is e.g. the case when a given terminal, and in particular a given printer, such as an Automated Ticketing and Boarding Pass (ATP) and / or Luggage Checker (BTP) printer, is to be used for check-in or boarding with another airline, which is another DCS used. In such situations, it is known that problems and disturbances occur due to incompatibilities. Such problems can cause significant delays and even require an IT expert to solve them.
    The object of the present invention is to improve the situation regarding the coupling and communication between the DCSs on the one hand and the terminals and / or printers on the other hand and to completely or partially avoid the aforementioned problems.
    This object is solved by the subject matter of the independent claims. Particularly advantageous embodiments are defined by the dependent claims.
    According to one aspect of the invention, the object is achieved by providing a flight data interface device. Such a flight data interface device comprises a terminal interface, wherein the terminal interface is designed to operatively couple the flight data interface device with a terminal, in particular a check-in counter and / or a workstation of an employee at the gate. The universal dispatch platform solution further includes a dispatching system (DCS) interface, the DCS interface being configured to operatively couple the universal dispatch platform solution to at least one DCS. Hereinafter, a flight data interface device in accordance with the present invention will also be referred to as a "universal dispatch platform solution" (UDPS). The terms "flight data interface device" and "universal dispatch platform solution" or UDPS are therefore to be understood as synonyms.
    The universal dispatch platform solution further includes a backup system as a functional unit. The backup system is coupled to the terminal interface and the DCS interface. The backup system is adapted to operate in a standby mode when there is operational coupling with the DCS. The backup system is designed to receive flight-relevant data from the DCS in standby mode, to store the data and to synchronize the stored data with data stored by the DCS. The backup system accordingly continuously reflects relevant data stored by the DCS. Hereinafter, a backup system in accordance with the present disclosure is also referred to as an "autonomous backup system" (RAS). The terms "reserve system" and "autonomous reserve system" or RAS are therefore to be understood as synonyms.
    The autonomous backup system is further configured to temporarily operate in an active mode in the event that operational coupling with the DCS is temporarily interrupted. In active mode, the autonomous backup system is designed to operate as DCS for the terminal. However, the functionality of the autonomous backup system in active mode is typically limited compared to the regular DCS. The autonomous reserve system or the flight data interface device is a typically computer-aided device with one or more processors and / or controllers, which can be supplemented by other peripheral circuits and / or components. Under the control of a corresponding program code (software or firmware), the processors or peripheral circuits implement the various functional modules according to the present disclosure, such as the DCS interface, the terminal interface, and, for example, a backup system, as explained below , Unless otherwise explicitly stated, the functional units of the Universal Dispatch Platform Solution may be implemented by or based on processors under the control of appropriate program code (software and / or firmware). However, some or all of the functional units may also be implemented as special dedicated circuits.
    Typically, the DCS is located at a remote location, for example in an airline planning center, as noted above. The operative coupling is typically done via an internet connection and, in principle, can also take place via another suitable remote communication interface and / or a remote communication network.
    The universal dispatch platform solution, as well as docked terminals and printers, is installed locally at the airport, particularly a departure airport, and part of the airport's technical infrastructure. The communication between the individual modules of the universal dispatch platform solution as well as the communication between the universal dispatch platform solution and coupled terminals and printers is achieved by a local communication interface and / or a local communication network, which is part of the technical infrastructure of the airport and the (Internet) communication network Communication with the DCS is different. The local communication may e.g. can be achieved via a local area network (LAN) and / or can also be completely or partially device-internally. The universal dispatch platform solution may also be fully or partially mobile.
    The autonomous backup system is configured to operate in the same manner as the DCS with respect to the operatively coupled terminal. The terminal can accordingly exchange data with the autonomous backup system in substantially the same manner as with the DCS.
    The synchronization is advantageously carried out on a continuous or quasi-continuous basis. That is, whenever new or updated relevant data is present in the DCS, it is transmitted to the autonomous backup system, which is updated accordingly.
    In some embodiments of the universal dispatch platform solution, the universal dispatch platform solution is adapted, after a previously temporarily suspended operational coupling with the DCS has been restored, to transmit data stored by the autonomous backup system to the DCS.
    By this transmission, the DCS is synchronized with the autonomous backup system (which is also referred to as "back-synchronization"). Such back-synchronization can be performed automatically. For this purpose, the autonomous backup system and / or the DCS may be adapted to automatically detect if the operative coupling between the Universal Dispatch Platform solution and the DCS is restored, and to trigger back-synchronization in this case. Alternatively or additionally, the back-synchronization can be triggered manually.
    When boarding is completed, however, relevant data, in particular relevant passenger data, are often transmitted from the DCS to the arrival airport prior to departure. In some embodiments, the universal dispatch platform solution, and in particular the autonomous backup system, is configured to establish operational communication with an arrival airport and to communicate relevant flight data to the arrival airport if the operational coupling of the DCS is interrupted when boarding is complete. This type of embodiment allows transmitting the relevant data from the universal dispatch platform solution, and more particularly from the autonomous backup system to the arrival airport, rather than from the DCS to the arrival airport, if operational coupling with the DCS is discontinued after completion of boarding and re-synchronization is not performed accordingly could be. Delivering the relevant data from the Universal Dispatch Platform solution at the departure airport to the destination airport allows the flight to start on time, even if the connection to the DCS is lost.
    In some embodiments of the universal dispatch platform solution, the autonomous backup system is configured to process passenger lists (PNLs) and / or additional cancellation lists (ADLs).
    In some embodiments of the universal dispatch platform solution, the autonomous backup system includes a backup server module and a backup RAS module. The backup server module is operatively coupled to the aforementioned DCS interface, or the DCS interface is part of the backup server module. The backup server module is configured to store and synchronize the data received from the DCS in standby mode as previously discussed.
    The backup RAS module of such embodiments is operatively coupled to the backup server module. The backup RAS module is adapted to provide data stored by the backup server module to the terminal and to temporarily act as DCS. Accordingly, the backup server module acts as the server for the backup RAS module, while the backup RAS module takes over the role of the DCS from the terminal.
    In some embodiments of the universal dispatch platform solution, the DCS interface is configured to couple the universal dispatch platform solution to a set of DCSs, and the universal dispatch platform solution further includes a DCS switch module. The DCS switching module of such embodiments comprises: a) a DCS selection module, the DCS selection module configured to receive user input for selecting a newly selected DCS from the set of different DCSs; b) an application and service stop module, the application and service stop module configured to stop applications and services operating on the terminal and / or printer from operably coupling to a previously selected DCS; c) a print data erase module, wherein the print data erase module is configured to control the execution of an erase procedure, the erase procedure comprising erasing print data stored in the printer from operative coupling with a preselected DCS; d) a startup control module, the startup control module configured to control the execution of a startup procedure selected from a set of different startup procedures, wherein the various startup procedures are hosted by the universal dispatch platform solution and correspond to the various DCSs of the set of DCSs, wherein each of the startup procedures, when started, configures the terminal for use with a specific DCS, the selected startup procedure configuring the terminal for use with the newly selected DCS.
    This type of embodiment allows for alternative use of one and the same terminal and / or printer as previously mentioned, along with a set of a plurality of DCSs, which are typically located at remote locations and may be distributed worldwide In particular, embodiment of the invention enables easy and convenient use of one and the same terminal and / or printer in connection with DCSs of different types and / or manufacturers. The selection of the DCS with the DCS selection module may e.g. conveniently done with a graphical user interface.
    The DCS selection module, the applications and services stop module, the print data erase module, and the startup module are functional units of the universal dispatch platform solution or flight data interface device, respectively.
    In general, at any given time, the terminal can only be used in conjunction with a single DCS. The universal dispatch platform solution of this type of embodiment, particularly the DCS switching module, is therefore adapted to enable an operative coupling of the terminal module with the previously selected DCS when the terminal and / or printer is configured for use with the newly selected DCS.
    Specifications for printers that can be used in conjunction with a universal dispatch platform solution according to the present disclosure are published in particular by the Association of European Airlines (AEA), which are used as a de facto worldwide standard. The universal dispatch platform solution may accordingly be adapted to operatively couple to a printer that conforms to the specifications and / or is compatible with the corresponding AEA specifications.
    The Applications and Services Stop Module and the Print Data Erase Module ensure successful connection and operation in conjunction with the newly selected DCS. Without such modules, establishing a successful operative connection with the newly selected DCS may not be possible and / or may in some instances cause operational errors due to still running services and / or print data stored in the printer. The execution of the delete procedure results in the printer being placed in a neutral or "clean" state in which it is ready to process then data originating from another DCS. Depending on the operationally-coupled DCSs and the number of operationally-coupled terminals, the autonomous backup system may include one or more DCS switch modules.
    In some embodiments, the universal dispatch platform solution is configured to interface with a set of terminals. In particular embodiments, where the universal dispatch platform solution is configured to interface with a number of DCSs and a number of terminals, an autonomous backup system backup server module may be configured to communicate through the DCS interface to one, multiple, or multiple DCSs ideally, to couple all DCSs of the set of DCSs. The autonomous backup system may accordingly secure more than one DCS of the set of DCSs simultaneously and / or alternatively. The backup RAR module is typically in one-to-one connection with a terminal, and there is a separate backup RAS module for each terminal.
    A method of configuring a terminal for use with a selected DCS may include the steps of: a) selecting the DCS from a set of DCSs; b) Running a stop procedure for applications and services. The stop procedure for applications and services includes stopping applications and services running on a terminal and / or a printer; c) performing a deletion procedure on the universal dispatch platform solution, the deleting procedure comprising deleting print data stored in a printer; d) selecting a selected startup procedure from a set of different startup procedures, the different startup procedures corresponding to the different DCSs, each of the startup procedures, when executed, configuring the terminal and / or the printer for use with the selected DCS; e) Execute the selected startup procedure.
    An unclaimed universal dispatch platform solution designed to alternatively couple the terminal to a DCS selected from a set of DCSs, as previously explained, may also be implemented without the autonomous backup system described above. Such an embodiment of a universal dispatch platform solution comprises: a) a terminal interface, the terminal interface being adapted to operatively connect the universal dispatch platform solution to a terminal, in particular a check-in counter and / or workstation of an employee at the gate couple; b) a dispatching system (DCS) interface, wherein the DCS interface is adapted to couple the universal dispatch platform solution to a set of DCSs; c) a selection module, the selection module configured to receive a user input for selecting a selected dispatch system from a set of different DCSs; d) a print data erase module, wherein the print data erase module is configured to control the execution of an erase procedure, the erase procedure comprising erasing print data stored in the printer; e) a startup control module, the startup control module configured to control the execution of a startup procedure selected from a set of different startup procedures, wherein the various startup procedures are hosted by the universal dispatch platform solution and correspond to the various DCSs of the set of DCSs, wherein each of the startup procedures, when started, configures the terminal for use with the newly selected DCS.
    In some embodiments of the universal dispatch platform solution, the universal dispatch platform solution is at least partially integral with the terminal.
    According to a further aspect of the invention, the object is achieved by a method for coupling a terminal, in particular a check-in counter and / or a workstation of an employee at the gate, with a DCS. Such a method comprises the following steps: a) determining whether operational coupling with a dispatching system (DCS) is available, and as a result of determining: b1) operatively coupling the terminal to the DCS to exchange data with the DCS; or b2) operatively coupling the terminal to an autonomous backup system operationally and controlling the autonomous one
    Reserve system to temporarily work as a DCS.
    The method can in particular be implemented with a universal dispatch platform solution according to an embodiment previously discussed and / or below by exemplary embodiments.
    In yet another aspect, the object is achieved by providing a computer program product comprising a non-transitory computer-readable medium having computer program code stored thereon. The program code may be obtained by software and / or firmware and is adapted to instruct a computer, in particular a processor of a computer, to operate as a universal dispatch platform solution according to one of the embodiments previously defined and / or below by way of example. The program code may be adapted to instruct a computing device, in particular a processor of a terminal, to execute a method according to one of the embodiments previously defined and / or in examples below. In particular, the computer may comprise one or more general-purpose computing devices, such as workstations and / or terminals, programmed with the aforementioned computer program code.
    Exemplary Embodiments In the following, exemplary embodiments in accordance with the present disclosure will be explained and discussed in more detail with additional reference to the drawings.
    FIG. 1 shows an exemplary embodiment of a universal dispatch platform solution in accordance with the present disclosure along with associated elements in a schematic, structural view; FIG.
    FIG. 2 shows another exemplary embodiment of a universal dispatch platform solution in accordance with the present disclosure along with associated elements in a schematic, structural view; FIG.
    Fig. 3; FIG. 12 shows yet another exemplary embodiment of a universal dispatch platform solution in accordance with the present disclosure along with associated elements in a schematic, structural view.
    In the following, reference is first made to Fig. 1 reference. The universal dispatch platform solution 1, or the flight data interface device of FIG. 1, comprises a DCS interface 10, a terminal interface 11 and an autonomous backup system 12. In operation, the DCS interface operatively couples the universal dispatch platform solution 1 to a typically remotely located one DCS 2 via a remote communication interface and / or a remote communication network, eg via Internet. The universal dispatch platform solution is implemented as a computer-aided device with one or more processors and / or controllers whose operation is controlled by a corresponding program code (software or firmware). Typically, the one or more processors and / or controllers are supplemented by further peripheral circuitry and / or components. Under the control of the program code (software and / or firmware), the one or more processors and / or controllers and potential peripheral circuits form the various functional modules of the universal dispatch platform solution, as will be explained in more detail below.
    The terminal interface 11 coupled in operation the universal dispatch platform solution 1 with a terminal 3. The terminal 3 may be in particular a check-in counter and / or a workstation of an employee at the gate. The terminal 3 is operatively coupled to a printer 4. In particular, the printer 4 may be an ATP printer and / or a BTP. Accordingly, the printer 4 is also coupled to the universal dispatch platform solution 1 via the terminal 3. Alternatively, the printer 4 may be directly coupled to the universal dispatch platform solution 1. A coupling between the universal dispatch platform solution 1, the terminal 3 and the printer 4 is achieved via a local communication interface, and / or achieved a local communication interface, which is different from the remote communication interface and / or a remote communication network. Some or all of the Universal Dispatch Platform Solution 1, the Terminal 3 and the Printer 4 may be fully or partially implemented in a structurally integral form. Furthermore, the printer 4 may not be present.
    The universal dispatch platform solution 1 further comprises the autonomous backup system 12, which is operatively connected to the DCS interface 10 and the terminal interface 11. In operation, the autonomous backup system 12 typically operates in a standby mode in which it synchronizes itself with the DCS 2 and mirrors relevant data stored by the DCS 2 in a local memory of the autonomous backup system 12. Relevant data, in particular relevant flight data and / or data changes in the DCS 2 are automatically transmitted to the autonomous reserve system 12.
    In the event that the operational coupling between the DCS 2 and the DCS interface 10 is temporarily interrupted, the autonomous backup system 12 serves as a temporary replacement for the DCS 2 and acts accordingly as a DCS but with limited functionality. In this situation, the terminal 3 and the printer 4 each communicate with the autonomous backup system 12 instead of the DCS 2.
    As previously explained in the general description, switching between the standby mode and the active mode in which the autonomous backup system 12 operates as DCS can be automatic and / or manual.
    In the following, reference is additionally made to FIG. 2. FIG. 2 shows another exemplary embodiment of a universal dispatch platform solution in accordance with the present disclosure along with associated elements in a schematic, functional view. With reference to FIG. 2, only those elements and features that were not present in the previously discussed embodiment and / or work in a different manner will be discussed.
    In the embodiment of Fig. 2, the DCS interface 2 is adapted to operatively couple the universal dispatch platform solution 1 to each of the set of DCSs 2a, 2b, 2c, ... 2n. In addition to the embodiment of FIG. 1, a DCS switch module 13 is further provided in the universal dispatch platform solution of FIG. 2. The DCS switch module 13 allows the terminal 3 and the printer 4 to selectively connect to each of the DCSs 2a ... 2n
    权利要求:
    Claims (11)
    [1]
    operatively to couple. The DCS switching module 13 includes a DCS selection module 130, an applications and services stop module 131, a print data erase module 132, and a startup control module 133. To explain the operation of the DCS switching module 13, it is assumed at the moment that the terminal 3 and the associated printer 4 is operatively coupled to one of the DCSs, for example DCS 2a. Through the DCS selection module 130, a user, for example, an employee at the check-in desk or an employee at the gate, can select any one of the other DCSs 2b, ... 2n. This selection can be made via any suitable user interface, for example a graphical user interface. After a new DCS has been selected, for example, DCS 2b, the internal logic of the DCS switch module 13 controls the execution of the application and service stop procedure via the applications and services stop module 131. Executing the application and service stop procedure results in all services and applications running on the terminal 3 and / or printer 4 and related to the DCS 2a being stopped in a controlled manner. In addition, the print data erasing procedure is executed via the print data erasing module 132. By executing the print data deletion procedure, data stored in the printer 4, in particular, pactabs resulting from the operative coupling with the DCS 2a, are deleted or deleted. Executing the application and service stop procedure and deletion procedure creates a "clean" environment for subsequent operative coupling with the newly selected DCS 2b. For establishing an operative coupling with the newly selected DCS 2b, the internal logic of the DCS switching module 13 controls the execution of a startup procedure via the startup control module 133. In the following, reference is additionally made to FIG. 3 shows another exemplary embodiment of a universal dispatch platform solution in accordance with the present disclosure along with associated elements in a schematic, functional view. In contrast to the previously described embodiments, the universal dispatch platform solution 1 of Fig. 3 is adapted for operative coupling with a plurality of terminals 3a, 3b, 3c, 3d. For example, each terminal 3a, 3b, 3c, 3d is shown with a connected printer 4a, 4b 4c, 4d. It should be noted that the number of four terminals and four printers is merely illustrative and exemplary. In the embodiment of Fig. 3, the autonomous backup system 12 has a two-part structure with backup server modules 120a, 120b and backup RAS modules 121a, 121b, 121c, 121d. The number of backup server modules and backup RAS modules is exemplary. Each of the backup RAS modules 121a ... 121d couples to a corresponding terminal 3a ... 3d and / or printer 4a ... 4d via a corresponding terminal interface 11a ... 11d. There is accordingly a one-to-one coupling between the backup RAS modules 121a ... 121d and the terminals 3a ... 3d and associated printers 4a ... 4d. A terminal is accordingly coupled to one and only one backup RAS module. The backup server modules 120a, 120b couple to the terminal interface 10 and a number of backup RAS modules 121a ... 121d, respectively. While each backup server module 120a, 120b may operatively couple to and interact with a number of backup RAS modules 121a... 121d, each of the backup RAS modules 121a ... 121d may only operatively dock one of the backup server modules 120a, 120b and cooperates with this each. For this type of embodiment, the backup server modules 120a, 120b locally store the data synchronized with the DCSs 2a ... 2n, as previously explained. For this type of embodiment, the autonomous backup system 12 - as a whole - is in standby mode when there is operational coupling between the DCS interface 10 and all DCSs 2a ... 2n. The autonomous backup system 12 is-as a whole-in active mode when operational coupling with at least one of the DCSs 2a... 2n is interrupted. Advantageously, the autonomous DCS backup system 12 operatively replaces only those DCSs to which the operative coupling is actually interrupted. DCSs in which the operational coupling is present can still communicate with the terminals 3a ... 3d without intervention by the autonomous backup system 12 and exchange data. Where the autonomous backup system 12 temporarily serves as DCS, the backup server module 120a and / or 120b each serve as a "server" which stores and provides the required data while the corresponding backup RAS module 121a ... 121 d - from the point of view of the terminal - assumes the role of the DCS. The DCS switching module 13 is shown by way of example as a common module that may be used to couple each of the data terminals 3a ... 3d to typically any of the DCSs 2a ... 2n. In alternative designs, separate DCS switch modules may be present for each terminal. claims
    A flight data interface device (1), comprising: a) a terminal interface (11) which is adapted to operate the flight data interface device (1) operatively with a terminal (3), in particular a check-in switch and / or a workstation of an employee at the gate; b) a DCS interface (10) adapted to couple the flight data interface device (1) to at least one DCS (2); c) a backup system (12) operably coupled to the terminal interface (11) and the DCS interface (10), wherein the backup system (12) is adapted to operate in a standby mode when operational Coupling with the DCS (2) is present, wherein the reserve system (12) is further adapted to receive in the standby mode relevant flight data from the DCS (2), to store the data and the stored data from the DCS (2 ), and wherein the backup system (12) is further configured to operate in an active mode and in an active mode in the event that the operative coupling with the DCS (2) is temporarily interrupted the terminal (3) to work as a temporary replacement of the DCS.
    [2]
    2. Flight data interface device (1) according to claim 1, wherein the flight data interface device (1) is designed after a previously temporarily interrupted operational coupling with the DCS (2) has been restored, the data from the backup system (12 ) are transmitted to the DCS (2).
    [3]
    3. Flight data interface device (1) according to one of the preceding claims, wherein the backup system (12) is adapted to handle flight data, in particular PNLs and ADLs.
    [4]
    The flight data interface device (1) according to one of the preceding claims, wherein the backup system (12) comprises a backup server module (120a, 120b), wherein the backup server module (120a, 120b) is operatively connected to the DCS server. Interface (10) and adapted to, in standby mode, store the data received from the DCS (2) and synchronize with the data stored by the DCS, the backup system (12) further comprising a back-up backup system module (121a , 121b, 121c, 121d) in operative coupling with the backup server module (120a, 120b), wherein the back-up backup system module (121a, 121b, 121c, 121d) is adapted to operate in the active mode Terminal (3) the data stored by the backup server module (120a, 120b) provide.
    [5]
    A flight data interface device (1) according to any one of the preceding claims, wherein the DCS interface (10) is adapted to connect the flight data interface device (1) to a set of DCSs (2a, 2b, 2c, ... 2n). operatively and the flight data interface device (1) further comprises a DCS switching module (13), wherein the DCS switching module (13) comprises: a) a DCS selection module (130), wherein the DCS selection module (130) thereto is configured to receive a user input for selecting a newly selected DCS from the set of different DCSs (2a, 2b, 2c, ... 2n); b) an applications and services stop module (131), the applications and services stop module (131) being adapted to operatively couple the running applications and services on a terminal (3) and / or printer (4) to a computer previously selected DCS (2a, 2b, 2c, ... 2n) to stop; c) a print data erase module (132), wherein the print data erase module (132) is adapted to control the execution of an erase procedure, the erase procedure comprising erasing print data stored in a printer (40) from operative coupling with stored in a preselected DCS; d) a startup control module (133), wherein the startup control module (133) is configured to trigger the execution of a startup procedure selected from a set of different startup procedures, wherein the various startup procedures are hosted by the flight data interface device (1) and correspond to the various DCSs of the set of DCSs (2a, 2b, 2c, ... 2n), each of the startup procedures, when started, the terminal (3) for data exchange with a specific DCS (2a, 2b, 2c, ... 2n), the selected startup procedure configuring the terminal for use with the newly selected DCS.
    [6]
    The flight data interface device (1) according to claim 5, wherein the deletion procedure comprises a pectab deletion procedure for ATPs and / or BTPs.
    [7]
    A flight data interface device (1) according to any one of the preceding claims, wherein the flight data interface device (1) is adapted to couple to a set of terminals (3a, 3b, 3c, 3d).
    [8]
    A device comprising a flight data interface device (1) according to any one of the preceding claims and a terminal (4), the flight data interface device (1) being at least partially integral with the terminal (4).
    [9]
    Method for coupling a terminal (4), in particular a check-in counter and / or a workstation of an employee at the gate, with a DCS (2), the method comprising the following steps: a) determining whether an operative coupling with a DCS (2), and as a result of the determination: b1) to operatively couple the terminal (3) to the DCS (2) for communicating relevant flight data with the DCS (2); or b2) operatively coupling the terminal (3) to a backup system (12) and controlling the backup system (12) to temporarily operate as DCS.
    [10]
    A computer program product comprising a non-transitory computer-readable medium having stored therein computer program code adapted to be loaded into the computer and then to instruct the computer, in particular a processor of the computer, as flight data. Interface device (1) according to one of claims 1 to 7 or to act as a device according to claim 8.
    [11]
    A computer program product comprising a non-transitory computer-readable medium having stored thereon computer program code adapted to be loaded into the computer and then to instruct the computer, in particular a processor of the computer, a method according to Claim 9 execute.
    类似技术:
    公开号 | 公开日 | 专利标题
    EP2769297B1|2020-07-08|DATA LOADING SYSTEM, PORTABLE DATA LOADING DEVICE AND METHOD TO LOAD SOFTWARE CONFIGURATIONS INto AN AIRCRAFT
    DE60130285T2|2008-05-29|Redundant input / output management unit, in particular a routing system
    DE102016105589A1|2016-09-29|Apply firmware updates in a zero-downtime system by selectively turning off and on hardware using a hypervisor layer
    DE112011102443T5|2013-06-20|Server management using a baseboard management controller to set up a wireless network
    DE60305998T2|2007-01-25|An apparatus, gateway, and method for loading information between aircraft on-board equipment and off-board charging equipment
    DE19954268B4|2005-07-21|Method and system for improving workflow in workflow management systems
    DE1449529B2|1971-09-02|INTERRUPTION DEVICE FOR A DATA PROCESSING SYSTEM
    DE19983497B4|2006-01-26|Remote transmission between file units
    DE112013000465B4|2017-08-17|Management of remote data replication
    DE202014002582U1|2014-07-11|Computer apparatus for use during the flight for an aircraft cabin crew
    DE102013215008A1|2014-03-27|Data mobility on a grid basis
    DE102011082291A1|2012-05-16|Controller for machine tool and machining-related data processing system provided therewith
    DE10212634A1|2002-10-10|Page description language that is designed for direct printing of multi-file formats
    DE3619660C2|1991-08-08|
    DE112013007469B4|2018-10-04|Communication system, standby device, communication method, and standby program
    DE102013103379A1|2014-10-09|Control and data transmission system for redundant process control and firmware update process
    CH710509B1|2017-06-15|Flight data interface device.
    DE10152530B4|2007-09-27|Workflow-friendly firmware updates for network devices
    DE60211211T2|2007-02-15|COMMUNICATION DEVICE, RECEPTION PROCESSING METHOD AND PROGRAM, AND COMPUTER READABLE MEDIUM ON WHICH THIS PROGRAM IS STORED
    EP3082001B1|2020-09-09|Method for expanding an automation device using a virtual field device and automation device
    DE19849962A1|1999-09-09|Distribution of printing between multiple printers
    DE102015208137A1|2015-11-12|Method and device for the universal control of networked devices
    DE102004017698A1|2005-11-10|Supervisory control and data acquisition system for network control system, has data acquisition components e.g. blocking devices, switching assignments and markings and usages of foreign vendors that are in respective integration platforms
    DE112012006909T5|2015-06-03|Control system management device
    DE102018201063A1|2019-07-25|Method and control device for operating a system
    同族专利:
    公开号 | 公开日
    CH710509A2|2016-06-15|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    法律状态:
    2017-09-29| PCAR| Change of the address of the representative|Free format text: NEW ADDRESS: BELLERIVESTRASSE 203 POSTFACH, 8034 ZUERICH (CH) |
    2020-05-29| PL| Patent ceased|
    优先权:
    申请号 | 申请日 | 专利标题
    CH16582014|2014-10-29|
    [返回顶部]